Hello Friends, I hope you are well. I developed an application for operators working in the field. This application is used for starting and finishing work orders and for waste entries. I ran into a problem when I deployed the application on the server. In this problem; I was sending a query to nodered via http in and getting a response. Because Nodered works with http, browsers did not see the queries as secure and blocked them. When I manually added the site as a secure site, the problem was solved, but can we do a work on https?

To add Node-RED via HTTPS, you need to either 1. Publish it on the internet and put something like cloudflare in front of it. additionally, you should add a password protection, so that not everyone ca naccess it 2. add a local certificate and then install the certificate on each device where you want to access from (really not recommended)

Since node-red lacks a good authentication one of my ideas to work around this was to use separate containers for each dashbord to work around the authentication problem.. This way you can limit which data each dashboard can access. Also you can use mqtt or redis to send/recieve data..

Actually the app works on the internet. I want it to be on the same network in the Node-Red connection anyway. If the device is on a different network, do not use the application. I set it according to this rule. Flow is; 1. The user first joins the MC's network. 2. Then he opens the login screen and logs in with his password. 3. Then the application lists the applications in the field. For this, it sends a post request to the MC. (http://192.168.10.226/nodered/listMachine). This is where the problem arises. Internet Browser is blocking the post request because https is not used. When I add HTTPS, node-red does not respond.

so you can login to nodered without http but your api-request gets denied ?

in local networks, HTTPS is unfortunately not possible (you can do it, but it will not solve your problem and will be very difficult)

I did not know that. Alternatively, I added a code in the application I wrote. Thanks to this, I see the application as safe in the browser and allow access to http via .htaccess. Seems to be resolved now 🙂

i do not understand your process fully.. can you show a screenshot ?

If you have 10 minutes, I can tell you faster over the google meet 😄

this should also work in theory

I solved the problem in the application I developed. I was getting HTTPs error for each post request. When I added this code the problem was solved.

i had just left the office, went to a machine in the factory and then went home for some cross country skiing..

Actually, I thought it was going to be over. I hope you didn't mess with me tonight. I'm reviewing the link. 😄

ahhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh

What is the benefit of using VueJS compared to do dashboards in node-red?

I will try to run it this way.

Nice. How about authorization, can you have different user for different dashboards?

i would consider calling MQTT from the frontend as weird (cannot really explain the reasons, just a gut feeling). mqtt should be handled by a backend and not from the frontend.

I actually have authorization in mind. But for this it may be necessary to create a user table in the UMH database. I plan to make this work after I develop and finalize the application. It will work like a competency matrix.

So there is no authorization available in vue? The authorization part is something i am looking at for dashboards since it is not good in node-red and i don't want to use grafana for all dashboards..

No. You can do it with Vue, but you have to define who has what authority somewhere. For this, the first method that comes to my mind is to create a user database and define what authority it has. Then you can redirect in vue according to the logged in user.

Nice. i will have a look and see if it is useful for me.